fix: #1354 - allow customisable leeway for JWT issued time in Apple provider …#1439
Open
harrowmykel wants to merge 1 commit intoSocialiteProviders:masterfrom
Open
Conversation
…by adding config key: jwt_issued_time_leeway
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
allow customisable leeway for JWT issued time in Apple provider by adding config key: jwt_issued_time_leeway.
The hardcoded fix for #1354 in #1357 still ended up being too low for my use case. Adding customisable/adjustable jwt_issued_time_leeway would fix it for everyone as suggested by @SvenRtbg in #1354 (comment)